|
![](/i/fill.gif) |
What is a good way to do collision testing? Approximate the object with
an enclosing box? And then how do you check it for intersections?
Also, is there a formula or macro out there can fill and only fill a
perspective view? Having objects outside the perspective projectors omitted
would optimize parse time.
--
Skip
Yadgar <j.b### [at] ndh net> wrote in message
news:3BEB0AA3.FCEB55FF@ndh.net...
> Hi Tracers!
>
> After removing my additional 64 megs module due to frequent crashes, I
> tested the performance with the remaining 256 megs (on an AMD K6-II/380
> MHz) by placing randomly 11, 000 of my plastic mouse wheels. Strangely,
> there is a concentration of objects near the origin (camera location is
> <0, 0.1, -0.4>, looking at <0, 0, 0>), though there are no quadratic
> terms containing the random variable...
>
> Rendering time: about 5:30 h, peak memory use: 309 megs
>
> The next step would be a collision detector...
>
> See you in Khyberspace -
> http://www.geocities.com/electricafghan/index-e.html
> Afghanistan Chronicle: http://www.ndh.net/home/bleimann/
>
> Yadgar
>
>
>
>
----------------------------------------------------------------------------
----
Post a reply to this message
|
![](/i/fill.gif) |